Prevent fork pull requests from running preview workflow - #21
Merged
Conversation
omeka-s Playground Preview
Try this PR in your browser This preview loads the plugin directly from the PR branch ZIP in Omeka-S Playground. |
Member
Author
|
Follow-up: #23 reverts this restriction. We will rely on GitHub's Require approval for all external contributors setting so maintainers can still run previews for legitimate fork contributions after manual approval. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Security rationale
The workflow has pull-request write permission. Restricting it to same-repository branches prevents external contributors from triggering a write-capable workflow.